test with subpath import (currently fails) #24
Conversation
|
It looks like I actually guessed right to begin with. What I didn't realize is that, when the NodeJS process exits, it doesn't always log everything. I figured out how to fix subpath import loading for my project: https://github.com/ajvincent/es-membrane/tree/20bea4e6483ea9f7f14facc5fbf9745415ae205a/build-utilities/loader-hooks The debug folder has a debug-by-logging hook which you can add multiple times, using the The subpath folder has my solution for resolving the subpath import just enough for tsimp to take over.
Porting this to tsimp should be straight-forward. |
I'm still trying to figure out why subpath imports don't work (#11). This pull request adds a test.
As far as I can tell, my previous attempt to fix this was in the wrong place entirely. When using relative paths, everything works. But when using a subpath import, tsimp's resolve and load hooks are never triggered for said import.